eCommerce Application
Authentication and Authorization
Criteria | Meet Specification |
---|---|
Demonstrate appropriate repository management using git. |
All project code has been organized properly and is in git, with proper branching. No extra files have been included using |
Demonstrate correct handling of authorization with proper security using JWT. |
App validates authentication of the user to let them into the project. Proper JWT headers are present and utilized correctly. The following are only accessible after authenticated:
|
Write proper tests for the above module and meet an acceptable code coverage level. |
Code coverage of 60% is met through tests. The tests include sanity and regression test cases and take care of negative tests as well. |
Metrics, Dashboards and Alerts
Criteria | Meet Specification |
---|---|
Identify the correct metrics to log, to monitor the system and Index metrics to Splunk. |
The code traces at least the following:
Logs are indexed to Splunk. The code sets up at least one alert (of your choice) for the system. For example: Screenshots are provided showing some query results and the alert setup. |
CI/CD
Criteria | Meet Specification |
---|---|
Demonstrate configuration and automation of the CI/CD pipeline. |
The submission manages build and deployment of the application with Jenkins:
|
Tips to make your project standout:
Setup Jenkins in docker and submit a screenshot of the result
Create a docker image for the project and deploy it to a docker container; submit a screenshot of the result